disaster recovery with
solaris™ cluster
White Paper April 2007
Sun Microsystems, Inc.
contents
introduction................................................................................................... 3 Why Business Continuity? ................................................................................... 3 Global Economy .......................................................................................... 3 Business Process Interdependencies ............................................................. 3 Regulatory and Legal Environment ............................................................... 4 24x7 Global Availability ............................................................................... 4 Traditional Disaster Recovery Solutions ................................................................ 5 Tape Backup ................................................................................................... 5 Redundancy.................................................................................................... 5 Local Clustering .............................................................................................. 5 Campus and Metropolitan Clustering ............................................................... 6 introducing sun cluster Geographic edition software......................................... 7 Solaris Cluster Software Business Models ............................................................. 7 Architecture ....................................................................................................... 8 Partnerships ................................................................................................... 9 Protection Groups ......................................................................................... 10 Supported Configurations .............................................................................. 11 Replicating Data ............................................................................................... 11 Sun StorEdge Availability Suite ...................................................................... 12 Sun StorEdge 9900 TrueCopy .......................................................................... 13 EMC SRDF ..................................................................................................... 13 Managing the Clusters ...................................................................................... 13 Discovering a Partner Loss ............................................................................. 13 Managed Takeover and Switchover ................................................................ 14 Inter Cluster Resource Manager (ICRM) .......................................................... 14 Returning to Normal ..................................................................................... 14 Secure Access ................................................................................................... 15 Solaris Cluster Software Services........................................................................ 15 conclusion ................................................................................................... 16 For More Information ........................................................................................ 16
3
Introduction
Sun Microsystems, Inc.
Chapter 1
introduction
Businesses have long understood that they need to plan for disasters. Before the turn of the century, organizations focused on preventing and avoiding environmental disasters such as fires or floods. And, much like businesses and people acquire insurance policies against the chance of a disaster, IT departments typically implement some kind of insurance in the form of redundancy to help applications recover from disasters. In a business world increasingly dependent on its IT infrastructure for daily operations, IT managers must focus not only on avoiding possible disasters, but also on recovering from the inevitable one. With the wide range of potential disasters—including terrorist attacks, hurricanes, extensive power grid failures, network threats such as worms and hackers, and even simple human error—businesses are constantly at risk. And every minute it takes to recover from a disaster can cost the organization in terms of lost sales and customers, harm to the company’s reputation, the cost of wages for people unable to perform their duties while the system or site is down, and the additional time it takes to play catch-up once the system is functional again. All of these factors can result in lost revenue and potentially, depending on the length of downtime, a total loss of the business itself. This white paper explores how Solaris™ Cluster can help organizations recover quickly from a disaster by enabling application and data access continuity across unlimited distances.
why Business continuity?
The unavoidable possibility of some disaster occurring, combined with the financial risk of extended downtime, are causing an evolution in thinking from simply recovering after disasters to continuing business despite disasters. In addition, there are a number of other trends currently influencing the development of business continuance strategies: Global economy The growing use of Internet-enabled applications and the proliferation of devices that access the Internet are driving requirements for around-the-clock, 24 x 7 access to corporate databases. This networked world has no tolerance for downtime, either planned or unplanned. Business Process interdependencies Some critical applications are so intertwined in the business that if any are interrupted, they can cause a series of disruptions that eventually lead to a complete breakdown of business processes. For example, a database operator could
4
Introduction
Sun Microsystems, Inc.
unknowingly enter a command causing an entire customer relationship management (CRM) system to come to a halt. While the problem is diagnosed and resolved, customer information must be recorded manually. The company must then face the challenge and cost of accurately and securely inputting the data while continuing normal operations. In addition, CRM systems are often dependent on other corporate databases such as order entry, marketing, inventory control, and shipping. Therefore, a failure of one database can cascade through the entire business infrastructure. regulatory and legal environment New regulations focusing on accountability have made business continuity a top priority for IT. Sarbanes-Oxley, the Health Insurance Portability and Accountability Act (HIPAA), the Graham-Leach-Bliley Act, and other industry- and country-specific regulations increase the penalties for companies whose risk-management practices are lacking or non-existent. Unfortunately, regulatory mandates on auditing data do not disappear during a disaster, making business continuity a critical component of a risk-management strategy. Additionally, businesses are recognizing the need for secure remote access during a disaster. 24x7 Global availability To help meet the evolving needs of global customers, many companies are investigating methods to extend the value of business continuity strategies by automatically transferring business functions to other geographies during their respective business hours. This capability can benefit companies in a number of ways, including freeing data centers for maintenance during off-business hours.
In developing a business continuity strategy, it’s important to recognize that there is often a difference between the actual availability of IT systems and the level of availability expected by the business and its users. In other words, users might expect their e-mail repositories to be immediately available after unplanned downtime, when in reality it might take several hours or even several days to recover the data from tape. IT managers and business users need to close this gap with proactive strategies to increase the availability of the IT infrastructure to both meet the recovery objectives of the business and maintain fiscal responsibility. Disaster recovery and business continuity plans require business users and IT managers to determine a recovery time objective (RTO) and recovery point objective (RPO) for each component of an application service, taking into account any interdependencies that might affect other applications. The RTO is defined by how quickly applications must be available in order for the business to resume functioning. For example, a shipping company’s customers may tolerate a shipping delay of a day or two. However, a financial services organization requires extremely high availability to reduce lost transactions to the smallest extent possible. RPO is the point in time
5
Introduction
Sun Microsystems, Inc.
to which the data must be restored in order for business to resume, measured by how much data an organization can afford to lose for particular application types. While a day’s worth of shipping data can probably be reconstructed from an order entry system, a day’s worth of lost medical scans at a hospital can mean the difference between life and death.
traditional disaster recovery solutions
Once the RTO and RPO for each application are determined, the appropriate level of availability can be implemented to meet those objectives. Traditional disaster recovery solutions still suffice for a number of application components.
tape Backup
Tape backup is still widely used and provides high availability of infrequently changing data, but not application services. Tape backups capture a point-in-time instance of data; any data created between that time and the next backup can potentially be lost if a disaster occurs. The data must then be restored, which can take hours to days, depending on the quantity of data. As a result, tape backup has a high RTO and RPO. This is usually adequate for businesses or applications that can tolerate longer recovery times and lower recovery points, such as archives of historical data.
redundancy
Businesses or applications that require shorter recovery times and higher RPO need more proactive strategies, including highly available clusters. A cluster is a collection of loosely coupled computing nodes that provide a single view of application services, including databases, Web, and file services. A cluster implemented using Solaris Cluster software offers restart, failover, and scalable services; capacity for modular growth; and a low entry price compared to fault-tolerant systems. In addition, it enables planned downtime of individual servers within a cluster.
Local clustering
A local cluster involves two or more physical machines (nodes) that share common disk storage and logical IP address. When an error is detected in one of the nodes, the cluster software will switch the clustered services over to the secondary machine. When planning a disaster recovery infrastructure, it’s important to note that local clustering provides a solid level of continuous service availability in the event of application, operating system, or hardware failure in a single data center, but it does not provide site-level disaster tolerance against even a minor disaster such as a fire or flood.
6
Introduction
Sun Microsystems, Inc.
campus and Metropolitan clustering
The next level of availability is to extend a cluster to another room or across a campus. Campus clustering enables components, such as nodes and shared storage, to be located tens of kilometers apart. In the event of a localized disaster such as a flood, fire, or building power outage, the surviving nodes can support the service for a failed node. This solution offers some site-level tolerance, but the short distance limits survivability of the cluster and its services for larger disasters like earthquakes or power grid outages. For greater availability across an increased distance like metropolitan areas, cluster nodes can be separated by hundreds of kilometers using Solaris Cluster software and technologies like dense wave division multiplexing (DWDM). The distance is then limited by the characteristics of the link, which must meet certain latency and errorrate specifications. It is important to consider that performance of storage shared between sites is dependent on the latency of the connecting links. All of the above solutions offer some level of availability to applications with different availability and budgetary needs. For example, it makes little financial sense to cluster Web servers for availability if they are replicated at multiple sites and the content changes infrequently. In that case, tape backups or data snapshots are probably sufficient. On the other hand, it is probably a good idea to cluster a shipping application across a campus to shield it against possible fires in the warehouse. And for other more mission-critical applications, metropolitan clustering provides the right combination of distance and cost. However, to provide true business continuity for applications that must continue to run despite the scope of a disaster, unlimited distance clustering is required. Sun Cluster Geographic Edition software provides this next step in the evolution of continuously available datacenters.
7
Introducing Sun Cluster Geographic Edition Software
Sun Microsystems, Inc.
Chapter 2
introducing sun cluster Geographic edition software
Solaris Cluster, a multi-system, multi-site disaster recovery solution that manages the availability of applications, services, and data across datacenters, now offers unlimited distance clustering through Sun Cluster Geographic Edition software. Sun Cluster Geographic Edition software is designed to help IT maintain data center availability and business continuity across unlimited distances and multiple sites during planned maintenance and in the event of a disaster. If the primary cluster becomes unavailable, Sun Cluster Geographic Edition software enables IT operators to start up the business services with replicated data on the secondary cluster. This software is intended for enterprise business services requiring a disaster recovery solution to survive disasters that have inflicted wide-area outage, failure, or destruction. It provides the protection that enterprises need to maintain 24x7 operations in support of their global customers.
Sun Cluster Geographic Edition
Sun Cluster Sun Cluster
Primary Site
Backup Site
In addition to Sun Cluster Geographic Edition software, Solaris Cluster includes the proven and dependable Sun Cluster software and Sun Cluster agents for more than 50 industry-leading applications. Sun Cluster software is the industry’s premier availability platform for improving the predictability and resilience of business-critical applications. It is designed to provide a highly available service-level management platform for single clusters that enables organizations to deploy applications as services and provide high availability, performance, and scalability of these services for the Solaris Operating System (Solaris OS) on both SPARC® and x64 platforms.
8
Introducing Sun Cluster Geographic Edition Software
Sun Microsystems, Inc.
Solaris Cluster provides different levels of robust availability, from basic single-node restart to metropolitan clustering to unlimited distance, and simplifies administration by enabling IT departments to manage availability with a single Sun Cluster graphical user interface (GUI).
solaris cluster software Business Models
Customers have several options for licensing Solaris Cluster software, including subscription-based models and perpetual right-to-use models. Options for subscription-based models are: • Subscribing to the Java Enterprise System, which offers a single, integrated, comprehensive software system with all of the critical enterprise network services that organizations need to deliver service-level agreements to their customers. Solaris Cluster software is a component of the Java Availability Suite, which in turn is a component of the Java ES. Customers can subscribe to the Java ES for $100 USD per employee, per year • Subscribing to the Java Availability Suite, which provides dependable application service-level management for a variety of network services, including Web and application, network identity, portal, communication and collaboration, and security services. Java Availability Suite licensing includes Sun Cluster software, Sun Cluster Geographic Edition software, Sun Cluster agents for more than 50 industry-leading applications, and Sun’s award-winning developer tools that are contained within Sun Java Studio Enterprise, Sun Java Studio Creator, and Sun Studio software. For organizations that aren’t ready to implement the entire Java ES but want to increase the availability of network services, the Java Availability Suite is available for $50 per employee, per year—making it an extremely costeffective business continuity solution for any size business or organization For those that specifically want only the Solaris Cluster components, these are available for download at no cost, offering a risk-free method to evaluate, develop, and deploy Sun software. Perpetual licenses and support are available for purchase when the software is deployed in a production environment. Customers that prefer to pay one-time fees for perpetual-right-to-use can buy licenses for different components of Solaris Cluster software: • One license per cluster node for Sun Cluster software • One license per cluster node for Sun Cluster Geographic Edition • One license per agent, per cluster With the options to either purchase licenses for Solaris Cluster point products or pay a subscription for Java ES or the Java Availability Suite that includes the right to use the Solaris Cluster components for one year as well as a range of other software products, customers have the flexibility to choose the model that best matches their business needs and budget.
9
Introducing Sun Cluster Geographic Edition Software
Sun Microsystems, Inc.
architecture
The Sun Cluster Geographic Edition software builds on the same hierarchical concepts as Sun Cluster software, providing a suite of tools to manage and configure geographically separated clusters and migrate services between sites. It is a layered extension of standard Sun Cluster software, employing multiple clusters of systems separated by long distances, a duplicated application configuration, and redundant storage infrastructure to replicate data between these clusters. This capability enables enterprises to adequately separate two cluster sites to help ensure that both sites are not afflicted by the same disaster. Because the data is replicated between clusters, application services can be migrated to a geographically separated secondary cluster in the event of a disaster or planned maintenance.
Partnerships
A partnership establishes heartbeat monitoring between two clusters running Sun Cluster Geographic Edition software. Clusters in the partnership exchange heartbeats over an Internet connection using Java Management Extensions Messaging Protocol and Secure Internet Protocol (IPsec) to monitor each other’s presence and health, as illustrated in Figure 1. IPsec enables the IT operator to set policies permitting or requiring secure datagram authentication and actual data encryption between clusters. It is also possible to use customized heartbeat modules to provide a heartbeat over alternative communication links such as e-mail, Hypertext Transfer Protocol (HTTP), satellite, and microwave towers. A single cluster can participate in more than one partnership with other clusters, but two clusters cannot be in more than one partnership with each other. A cluster pair can be configured as active-active or active-standby. In active-active, a pair of sites can function both as a primary site as well as a secondary site to each other. With active-standby, one site is the active primary site, while the other is a passive secondary site in standby mode. These two methods provide a cost-effective and flexible disaster recovery solution, enabling enterprises to fully utilize both Sun Clusters, or simply keep the secondary Sun Cluster on standby.
Heartbeat
Cluster-Paris Figure 1. A Cluster Partnership
Cluster-New York
10
Introducing Sun Cluster Geographic Edition Software
Sun Microsystems, Inc.
Protection Groups
Protection groups are relationships defined in the Sun Cluster Geographic Edition configuration that enable a set of clusters to tolerate and recover from disaster by managing resource groups for services. A protection group contains application resource groups and properties for managing data replication for those application resource groups. The configuration for a protection group is identical on partner clusters. Protection groups link an application in a resource group with the application data that should be replicated. This linkage and replication enable the application to fail over seamlessly from one cluster to another cluster.
Protection Group
Primary Site
Admin. Client
Backup Site
Protection Group
A cluster can be defined in more than one protection group and have a different role in each protection group. For example, the primary cluster of one protection group can also be the secondary cluster of another protection group, as shown in Figure 2.
Partnership Partnership
Cluster-London
Primary for application resource group 1
Cluster-Rome Protection Group 1
Secondary for application resource group 1
Cluster-Berlin
Primary for application resource group 2
Protection Group 2
Secondary for application resource group 2
Figure 2. Three Clusters in Protection Groups
11
Introducing Sun Cluster Geographic Edition Software
Sun Microsystems, Inc.
supported configurations
Sun Cluster Geographic Edition software supports replication from a multinode cluster to a single-node cluster, from a multinode cluster to a multinode cluster, and in an N+1 configuration, where multiple clusters are located at multiple sites and are communicating with a single backup cluster (see Figure 3). Multinode-tosingle-node and N+1 configurations can provide a cost-effective business continuity solution for enterprises with limited resources or with multiple primary sites that need to be protected.
ONE-WAY DATA REPLICATION One site backs up multiple sites
Paris Geneva Berlin
Rome
BI-DIRECTIONAL DATA REPLICATION Each site backs up the other
San Francisco, CA Paris, France
ONE-WAY DATA REPLICATION Multi-node to single-node
San Francisco, CA London
Figure 3. Supported Configurations
replicating data
Data replication is the process of continuously copying data from the primary cluster to the secondary cluster. Sun Cluster Geographic Edition software currently supports Sun StorEdge™ Availability Suite software, Sun StorEdge 9900 TrueCopy software and EMC SRDF for data replication. All three of these products support synchronous and asynchronous replication modes.
12
Introducing Sun Cluster Geographic Edition Software
Sun Microsystems, Inc.
In synchronous mode replication, a write operation to the primary cluster is not confirmed as complete until the remote cluster is updated. Synchronous replication forces the software to wait until the primary cluster receives an acknowledgment of the receipt of the data from the secondary cluster before returning to the application. Synchronous replication is intended to provide 100 percent synchronization between the primary and secondary clusters, potentially reducing data loss in the event of a disaster. The disadvantages of this method are possible performance degradation as the primary application waits for the secondary to write, and the cost of operation as lower-latency communications lines are needed to help reduce the wait just mentioned. In asynchronous mode replication, data is written to the primary cluster and to a local asynchronous queue. A write operation is confirmed as complete before the remote cluster is updated. Later, write operations that have accumulated in the asynchronous queue are forwarded in sequence to the remote peer. The disadvantage of this method is possible data loss. Because of the nature of asynchronous mode replication, the secondary cluster is always somewhat out of sync with the primary cluster; how far out of sync depends on how much data is in the asynchronous queue at the time of a disaster. Fortunately, because Sun Cluster Geographic Edition software supports replication software providing both methods, organizations can mix and match replication modes to best suit the needs of individual application services. For example, it might not make sense, both from a performance and an economic standpoint, to replicate an entire Oracle database from the primary cluster to the secondary cluster. If the application can tolerate a few minutes of downtime, it might be necessary to replicate only the online logs in synchronous mode while maintaining a standby Oracle database at the secondary cluster. This way, if a disaster occurs at the primary site, the standby database can be started fairly quickly in production mode with little data loss by applying the synchronized online logs. On the other hand, if the application needs to be available almost immediately following a disaster, the entire database can be replicated using synchronous mode for the logs and asynchronous mode for the remainder of the application, in which case the secondary database is simply started in production mode. Sun Cluster Geographic Edition software also supports protection groups that do not require data replication, offering flexibility for environments that handle data replication differently. In addition, Sun is constantly testing and adding support for more replication features and products. Please see the Web pages listed in the “For More Information” section for a current list of supported products.
13
Introducing Sun Cluster Geographic Edition Software
Sun Microsystems, Inc.
sun storedge availability suite
Sun StorEdge Availability Suite software is a host-based solution that includes both point-in-time copy and remote mirroring capability. The remote mirroring capability allows data to be mirrored to multiple remote secondary sites in both synchronous and asynchronous modes. Because the software is host-based, it can access any storage, including non-Sun storage, supported on the Solaris OS. The software design is link-neutral, meaning it can use any Sun network adapter supporting TCP/IP. When replicating data, Sun StorEdge Availability Suite software preserves write-order consistency using volume grouping. That is, the software makes sure that write operations to the secondary site occur in the same order as the write operations to the primary site. This helps ensure the data on the secondary site is consistent with data on the primary site and does not compromise an attempt to recover the data if a disaster occurs at the primary site. In the event of a planned or unplanned outage, remote mirror software maintains per-device bitmap volumes that are marked to indicate changed blocks. This helps speed and optimize resynchronization between clusters after planned or unplanned downtime because the software has to resynchronize only blocks that have changed. In addition, the Sun StorEdge Availability Suite software is integrated with Sun Cluster software for enhanced availability. Both the remote mirror primary and secondary hosts can failover to another host in their local cluster to help ensure the continuity of the data replication process within the clusters.
sun storedge 9900 truecopy
Sun StorEdge 9900 TrueCopy software is supported by Sun Cluster Geographic Edition software for replicating data residing on Sun StorEdge 9900 series storage systems and provides similar functionality to Sun StorEdge Availability Suite. The software is a storage-based replication facility that provides host-independent data replication for geographically separated clusters. Sun StorEdge 9900 TrueCopy provides the highperformance that today’s global businesses demand by offloading data replication from the host, and it also enables increased scalability by supporting Oracle RAC.
eMc srdF
EMC SRDF software is also supported by Sun Cluster Geographic Edition software for replicating data on one or more physically separate target Symmetrix systems, which can be located across the globe.
14
Introducing Sun Cluster Geographic Edition Software
Sun Microsystems, Inc.
Managing the clusters
One of the key advantages of Sun Cluster Geographic Edition software is Sun Cluster Geographic Edition GUI, enabling a single point of management of remote partner clusters in a Sun Cluster Geographic Edition environment. The Sun Cluster GUI allows IT operators to configure, control, and monitor partnerships, protection groups, heartbeats, and the Sun Clusters at each site. It uses SSL for secure communication and role-based access control (RBAC) rights to control end-user access to cluster operations. In addition, all management functions are available via a command line interface (CLI), offering IT operators the flexibility to create custom scripts for distinct environments.
discovering a Partner Loss
Sun Cluster Geographic Edition software notifies IT operators when the cluster heartbeat at the primary or secondary sites times out or makes a recovery. A cluster failure occurs when all nodes of a cluster shut down. The software can be configured to notify via a status flag in the Sun Cluster GUI, to send e-mail, or to execute scripts; the heartbeat time-out period can be set to a value that best meets the needs of the workload and distance between the two sites. Heartbeats could also be lost when a cluster loses access to the public network and no communication occurs between partner pairs. For this reason, Sun Cluster Geographic Edition software is designed for managed rather than automatic migration between sites.
Managed takeover and switchover
Sun Cluster Geographic Edition software provides two methods for migrating services between sites: managed switch over and takeover. In the event of a switchover or takeover, Sun Cluster Geographic Edition software can be configured to automatically execute a script to perform reconfiguration including, but not limited to, a DNS update. Managed switchover provides a mechanism to execute a transparent migration of services from the primary cluster to the secondary cluster for planned events such as maintenance and 24x7 work around the globe. During a managed switchover, the primary cluster remains connected to the secondary cluster and coordinates the migration of services with the secondary cluster to help ensure minimal or no data loss or data corruption. In the event of a large-scale outage such as a power failure or other disaster, the takeover feature enables IT operators to initiate a business continuity procedure by starting cluster-controlled application services—with associated replicated data— at the secondary site with a single, easy-to-use click command in the Sun Cluster GUI. Unlike a managed switchover, the primary cluster is not connected to the secondary cluster and cannot synchronize the data. The secondary site takes over the data and initiates application-specific recovery procedures.
15
Introducing Sun Cluster Geographic Edition Software
Sun Microsystems, Inc.
inter cluster resource Manager (icrM)
The Inter Cluster Resource Manager maps application resources with replicated data, and manages each of these protection groups as a unit between two geographically dispersed Sun Cluster sites. This helps ensure that in a takeover or switchover, application services running on clusters with multiple applications use the correct replicated data.
returning to Normal
What happens if a cluster in a partnership returns to normal? When the failed cluster restarts, the IT operator has the choice to go back to the original configuration or stay with the failover configuration. Sun Cluster Geographic Edition software supports two kinds of failback: failbackswitchover and failback-takeover. During a failback-switchover, applications are brought online on the original primary cluster after the primary cluster’s data is resynchronized with the data on the secondary cluster, bringing it up to date with any changes that occurred to the data after the failover. During a failback-takeover, applications are brought back online on the original primary cluster and use the current data on the primary cluster. Any updates that occurred on the secondary cluster are discarded.
secure access
A key area of business continuity (as well as compliance) is access management— making sure all users and customers are able to access information quickly and securely during a disaster. One technology that has emerged as a leading solution for remote access is Secure Sockets Layer (SSL) virtual private networks (VPNs). Sun Java System Portal Server Secure Remote Access software delivers secure Internet or extranet access to both internal portals and intranet applications through VPN and any Java technology-enabled browser. Like Sun Cluster, Java System Portal Server Secure Remote Access software is a component of the Sun Java Enterprise System and is fully integrated with the range of products included in the Java ES, which is available by subscription. By delivering secure access to personalized portal information over any Internet or extranet connection, the Java System Portal Server Secure Remote Access software can enable secure remote access to application services continuously, even during disasters.
16
Introducing Sun Cluster Geographic Edition Software
Sun Microsystems, Inc.
solaris cluster software services
A comprehensive business continuity plan must consider every aspect of the business if there is a catastrophe, including where people will relocate, e-mail, and secure access. To meet this need, Sun offers a myriad of services, solutions, and partners to help address these issues. Sun’s trained engineers and certified Sun partners can install and set up Sun Cluster and Sun Cluster Geographic Edition software correctly and quickly with a final deliverable of cluster reference documentation. This enables IT staff to stay focused on tasks that are important to the business, and helps avoid system failure due to improper installation and configuration. In addition, a Business Continuity Workshop and the SunReadySM Availability Assessment are available to help IT managers determine how best to deploy disaster recovery solutions utilizing Solaris Cluster. For more information on Sun Continuity and Recovery Services, see: http://www.sun.com/service/storage/continuity_recovery.xml.
17
Conclusion
Sun Microsystems, Inc.
Chapter 3
conclusion
As business has become dependent upon its IT systems for daily operations, the potential damage of a disaster has grown exponentially. Businesses need more than data availability; they need service continuity in order to stay responsive to customers, comply with government regulations, control insurance premiums, maintain productivity, and reduce financial risk—regardless of events. The Sun Cluster Geographic Edition software builds on a tried and trusted solution, extending Sun Cluster software and incorporating market-leading replication technology to help organizations create solid business continuance plans to mitigate business interruptions due to disasters. To ensure that organizations get the full benefits of Sun Cluster and Sun Cluster Geographic Edition software, Sun’s trained engineers and certified Sun partners can install and set up the solution correctly and quickly. In addition, Sun offers a range of training opportunities. Solaris Cluster, featuring Sun Cluster software, Sun Cluster Geographic Edition software, and agents for the industry’s leading applications, gives enterprises the confidence that even when a disaster strikes, their applications will keep running— and so will their businesses.
For More information
To learn more about Solaris Cluster or to learn how Sun can help build competitive advantage with a Sun business continuity solution, contact a local Sun sales representative. This table identifies other sources of information related to Sun products and solutions.
Description Solaris Cluster Get the Software Solaris Cluster Case Study: Austin American-Statesman Solaris Cluster Documentation Center Solaris Cluster Training Offer Sun software Solaris Sun Java Enterprise System Sun Java System Portal Server Secure Remote Access software Sun Continuity and Recovery Services Web site url sun.com/cluster sun.com/software/solaris/cluster/get.html sun.com/customers/index.xml?c=austin.xml docs.sun.com/app/docs/doc/820-0335/6nc35dge2?a=view sun.com/training/savings/cluster.xml sun.com/software sun.com/solaris sun.com/software/javaenterprisesystem/index.jsp sun.com/software/products/portal_sra/ sun.com/service/storage/continuity_recovery.xml
Disaster Recovery with Solaris™ Cluster
Sun Microsystems, Inc.
Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 USA Phone 1-650-960-1300 or 1-800-555-9SUN (9786) Web sun.com
©2007 Sun Microsystems, Inc. All right reserved Sun, Sun Microsystems, the Sun logo, Java, Solaris, and SunReady services are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. All SPARC trademarks are used under license and are trademarks or registered marks of SPARC International, Inc. in the U.S.and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. SunWIN # 505448 Lit # SWWP12853-0 5/07